⬆️(dependencies) update js dependencies #1375
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=80&v=4){kind=small}
renovate
bot
added
automated
|
Size Change: +5.1 kB (+0.14%) Total Size: 3.68 MB
|
renovate
bot
force-pushed
the
renovate/js-dependencies
branch
13 times, most recently
from
611b0dc to
bf00dad
Compare
renovate
bot
force-pushed
the
renovate/js-dependencies
branch
12 times, most recently
from
e0bce82 to
3f02602
Compare
AntoLC
force-pushed
the
renovate/js-dependencies
branch
10 times, most recently
from
1374e90 to
be5dc6c
Compare
There was a problem hiding this comment.
Pull Request Overview
This PR updates JavaScript dependencies across the project, with the major changes involving upgrading BlockNote packages from 0.37.0 to 0.40.0, Hocuspocus from 2.x to 3.x, and various other supporting library updates. The upgrades require significant changes to custom block implementations, collaboration server configuration, and several API adaptations for compatibility with the new versions.
Key Changes:
- Upgraded BlockNote packages (0.37.0 → 0.40.0) requiring restructuring of custom blocks (Callout, PDF, Image) to comply with new implementation patterns
- Migrated Hocuspocus server and provider from v2.15.2 to v3.2.5, updating connection handling and API usage
- Updated mutation hooks to support new TanStack Query v5.90.2 callback signatures (added
onMutateResultparameter)
Reviewed Changes
Copilot reviewed 64 out of 68 changed files in this pull request and generated 6 comments.
Show a summary per file
| File | Description |
|---|---|
| package.json files | Dependency version bumps across all frontend packages and e2e tests |
| hocuspocusServer.ts | Updated Hocuspocus server initialization and connection API for v3 |
| Custom block components | Refactored block specifications to use new BlockNote factory pattern |
| Mutation hooks | Updated callback signatures for new TanStack Query parameters |
| Provider store | Enhanced connection state management with ready/synced states |
| E2E tests | Updated selectors and assertions for BlockNote DOM structure changes |
| Export mappings | Removed custom divider block in favor of BlockNote default |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
|
|
||
| export function useUpdateDocLink({ | ||
| onSuccess, | ||
| listInvalideQueries, |
There was a problem hiding this comment.
Corrected spelling of 'listInvalideQueries' to 'listInvalidQueries'.
Copilot uses AI. Check for mistakes.
There was a problem hiding this comment.
I will do it in a separate PR.
src/frontend/apps/impress/src/features/docs/doc-editor/components/custom-blocks/PdfBlock.tsx
Show resolved
Hide resolved
src/frontend/apps/impress/src/features/docs/doc-management/stores/useProviderStore.tsx
Show resolved
Hide resolved
...frontend/apps/impress/src/features/docs/doc-editor/components/custom-blocks/CalloutBlock.tsx
Show resolved
Hide resolved
AntoLC
force-pushed
the
renovate/js-dependencies
branch
from
be5dc6c to
6408604
Compare
Ovgodd
approved these changes
Oct 22, 2025
There was a problem hiding this comment.
I’ve tested the app locally after all dependency upgrades:
Editor and custom blocks (Callout, Image, PDF, Divider) behave correctly, no flicker or rendering issues.
I also checked dependency versions, everything seems to be aligned except @blocknote/server-util, still at 0.40.0 while others are 0.41.1.
Nice job !
Ovgodd
approved these changes
Oct 22, 2025
There was a problem hiding this comment.
I’ve tested the app locally after all dependency upgrades:
Editor and custom blocks (Callout, Image, PDF, Divider) behave correctly, no flicker or rendering issues.
I also checked dependency versions, everything seems to be aligned except @blocknote/server-util, still at 0.40.0 while others are 0.41.1.
Nice job !
AntoLC
force-pushed
the
renovate/js-dependencies
branch
from
6408604 to
4051e72
Compare
Version 4.0.0 is not yet compatible with UiKit, better to wait.
Recent upgrade of @tanstack/react-query to version >5.90 introduced a breaking change in the onSuccess and onError callback signatures for the useMutation hook. The context parameter has been replaced with an onMutateResult parameter, which provides information about the result of the onMutate callback.
Blocknote now has a built-in divider block, so we can remove our custom implementation.
Last release of Blocknote introduced breaking changes for custom blocks. We adapted our custom blocks to the new implementation. "code-block" is considered as a block now, we update the way to import and use it. The custom blocks should be now more tiptap friendly.
AntoLC
force-pushed
the
renovate/js-dependencies
branch
from
4051e72 to
196d1d7
Compare
The last version of Blocknote seems to have a conflict with hocuspocus 2.15.2, it is a good moment to upgrade to hocuspocus 3.2.5.
Move the `useUpdateDocLink` hook from the `doc-management` feature to the `doc-share` feature to better align with its functionality related to document sharing.
When we open the share modal, the requests were then in cache, if other users where interacting with the share settings in parallel, we would not see the changes until the cache expired. We now force a fresh fetch of the data when opening the share modal, it ensures we always have the latest data when opening the modal.
The tests e2e highlighted a problem where content was lost during synchronization. This bug started to occurs after upgrading Blocknote to 0.41.1 version. It seems to happen only when the initial document is empty and 2 users are collaborating, so before the first minute. We now initialize the editor only when the y-doc has attempted to sync. This should ensure that all updates are applied before the editor is initialized.
AntoLC
force-pushed
the
renovate/js-dependencies
branch
from
196d1d7 to
145c688
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Note
Mend has cancelled the proposed renaming of the Renovate GitHub app being renamed to
mend[bot].This notice will be removed on 2025-10-07.
This PR contains the following updates:
0.37.0->0.40.00.37.0->0.40.00.37.0->0.40.00.37.0->0.40.00.37.0->0.40.00.37.0->0.40.00.37.0->0.40.00.37.0->0.40.05.2.5->5.2.70.16.1->0.16.215.5.3->15.5.43.2.3->4.0.01.55.0->1.55.14.3.0->4.3.110.11.0->10.17.010.11.0->10.17.010.11.0->10.17.05.86.0->5.91.05.87.4->5.90.25.87.4->5.90.26.8.0->6.9.122.18.1->22.18.819.1.12->19.2.019.1.9->19.2.08.43.0->8.45.08.43.0->8.45.05.0.2->5.0.41.0.1->1.3.161.12.0->1.12.210.0.0->10.1.017.2.2->17.2.39.35.0->9.37.015.5.3->15.5.47.6.8->7.11.025.5.2->25.5.330.1.3->30.2.026.1.0->27.0.04.15.3->4.16.115.5.3->15.5.41.1.1->2.1.71.264.2->1.271.019.1.1->19.2.01.12.1->1.13.019.1.1->19.2.015.7.3->16.0.016.24.0->16.25.039.0.0->39.0.129.4.1->29.4.45.9.2->5.9.35.101.3->5.102.0Release Notes
TypeCellOS/BlockNote (@blocknote/code-block)
v0.40.0Compare Source
🚀 Features
🩹 Fixes
❤️ Thank You
v0.39.1Compare Source
🩹 Fixes
❤️ Thank You
v0.39.0Compare Source
🚀 Features
❤️ Thank You
v0.38.0Compare Source
🚀 Features
🩹 Fixes
❤️ Thank You
fontsource/font-files (@fontsource/material-icons)
v5.2.7Compare Source
v5.2.6Compare Source
vercel/next.js (@next/eslint-plugin-next)
v15.5.4Compare Source
Core Changes
Misc Changes
Credits
Huge thanks to @yiminghe, @huozhi, @devjiwonchoi, @mischnic, @lukesandberg, @ztanner, @icyJoseph, @leerob, @fufuShih, @dwrth, @aymericzip, @obendev, @molebox, @OoMNoO, @pontasan, @styfle, @HondaYt, @ryuapp, @lpalmes, and @ijjk for helping!
microsoft/playwright (@playwright/test)
v1.55.1Compare Source
Highlights
#37479 - [Bug]: Upgrade Chromium to 140.0.7339.186.
#37147 - [Regression]: Internal error: step id not found.
#37146 - [Regression]: HTML reporter displays a broken chip link when there are no projects.
#37137 - Revert "fix(a11y): track inert elements as hidden".
Browser Versions
This version was also tested against the following stable channels:
diegomura/react-pdf (@react-pdf/renderer)
v4.3.1Compare Source
Patch Changes
#3124
dcc7b403Thanks @pcorpet! - feat(pdfdownloadlink): add a ref to the link componentUpdated dependencies [
beaffd3d,a99d10fb,5cbe2fb0,ec063bec]:getsentry/sentry-javascript (@sentry/nextjs)
v10.17.0Compare Source
Important Changes
feat(nuxt): Implement server middleware instrumentation (#17796)
This release introduces instrumentation for Nuxt middleware, ensuring that all middleware handlers are automatically wrapped with tracing and error reporting functionality.
fix(aws-serverless): Take
http_proxyinto account when choosinguseLayerExtensiondefault (#17817)The default setting for
useLayerExtensionnow considers thehttp_proxyenvironment variable.When
http_proxyis set,useLayerExtensionwill be off by default.If you use a
http_proxybut would still like to make use of the Sentry Lambda extension, exemptlocalhostin ano_proxyenvironment variable.Other Changes
beforeSendSpan(#17815)Internal Changes
v10.16.0Compare Source
replay_is_bufferingflag (#17752)instrumentAnthropicAiClientbreaking MessageStream api (#17754)Internal Changes
publish_releasecommand (#17797)import-in-the-middlewhen building the Lambda layer (#17780)[email protected]due to@vercel/nftincompatibility (#17777)" (#17784)[email protected]due to@vercel/nftincompatibility (#17777)v10.15.0Compare Source
Important Changes
feat(cloudflare): Add honoIntegration with error-filtering function (#17743)
This release adds a
honoIntegrationto@sentry/cloudflare, which exposes ashouldHandleErrorfunction that lets you define which errors inonErrorshould be captured.By default, Sentry captures exceptions with
error.status >= 500 || error.status <= 299.The integration is added by default, and it's possible to modify this behavior like this:
feat(node): Add instrumentation for hono handler (#17428)
This PR enhances the Hono integration by adding comprehensive handler instrumentation, error handling capabilities.
feat(aws): Enable Lambda extension by default when using the Lamba layer (#17684)
feat(browser): Add
setActiveSpanInBrowserto set an active span in the browser (#17714)This PR adds a feature to the browser SDKs only: Making an inactive span active. We do this to enable use cases where having a span only being active in the callback is not practical.
Other Changes
0andundefinedresource timing values (#17751)Internal Changes
@typescript-eslint/no-unnecessary-type-assertionrule (#17728)es2020everywhere (#17709)Work in this release was contributed by @Karibash. Thank you for your contribution!
v10.14.0Compare Source
Important Changes
feat(cloudflare,vercel-edge): Add support for Google Gen AI instrumentation (#17723)
The SDK now supports manually instrumenting Google's Generative AI operations in Cloudflare Workers and Vercel Edge Runtime environments, providing insights into your AI operations. You can use
const wrappedClient = Sentry.instrumentGoogleGenAIClient(genAiClient)to get an instrumented client.Other Changes
WeakRefwhen storing it on spans (#17712)Internal Changes
v10.13.0Compare Source
Important Changes
feat(browser): Add option to explicitly end pageload span via
reportPageLoaded()(#17697)With this release you can take manual control of ending the pageload span. Usually this span is ended automatically by the SDK, based on a period of inactivity after the initial page was loaded in the browser. If you want full control over the pageload duration, you can tell Sentry, when your page was fully loaded:
Note that if
Sentry.reportPageLoaded()is not called within 30 seconds of the initial pageload (or whatever value thefinalTimeoutoption is set to), the pageload span will be ended automatically.feat(core,node): Add instrumentation for
GoogleGenerativeAI(#17625)The SDK now automatically instruments the
@google/generative-aipackage to provide insights into your AI operations.feat(nextjs): Promote
useRunAfterProductionCompileHookto non-experimental build option (#17721)The
useRunAfterProductionCompileHookoption is no longer experimental and is now a stable build option for Next.js projects.feat(nextjs): Use
afterProductionCompilehook for webpack builds (#17655)Next.js projects using webpack can opt-in to use the
useRunAfterProductionCompileHookhook for source map uploads.feat(nextjs): Flip default value for
useRunAfterProductionCompileHookfor Turbopack builds (#17722)The
useRunAfterProductionCompileHookoption is now enabled by default for Turbopack builds, enabling automated source map uploads.feat(node): Do not drop 300 and 304 status codes by default (#17686)
HTTP transactions with 300 and 304 status codes are now captured by default, providing better visibility into redirect and caching behavior.
Other Changes
onSuccesstohandleCallbackErrors(#17679)consoleLoggingIntegration(#17703)oscontext (#17720)thirdPartyErrorFilterIntegration(#17693)thiscontext for vercel AI instrumentation (#17681)Internal Changes
reportPageLoaded(#17724)getTestMatrix(#17673)SyncPromisewhere not needed (#17641)ignoreSpans(#17692)module_metadataassignment and cleanup functions (#17696)HandleDocumentRequestFunction(#17680)Work in this release was contributed by @Olexandr88. Thank you for your contribution!
v10.12.0Compare Source
Important Changes
ref: Add and Adjust error event
mechanismvaluesThis release includes a variety of changes aimed at setting the
mechanismfield on errors captured automatically by the Sentry SDKs. The intention is to clearly mark which instrumentation captured an error. In addition, some instrumentations previously did not yet annotate the error as handled or unhandled which this series of PRs corrects as well.Relevant PRs
Released in
10.12.0:mechanismon error events captured by astro middleware (#17613)mechanismof errors captured in Bun.serve (#17616)mechanismsand durable object origin (#17618)mechanismincaptureConsoleIntegration(#17633)mechanism(#17622)linkedErrorsmechanism logic (#17600)mechanismof errors caught byglobalHandlersIntegration(#17635)mechanisms (#17543)mechanismto cron instrumentations (#17544)mechanism.typeto worker thread errors fromchildProcessIntegration(#17578)mechanismofonUnhandledRejectionandonUnhandledExceptionintegrations (#17636)mechanism.typein error events (#17599)reactErrorHandlerand adjust mechanism inErrorBoundary(#17602)captureRemixServerException(#17629)replayIntegrationin debug mode (#17606)mechanismto error captured bywithSentryErrorBoundary(#17607)mechanismof error events (#17646)Released in
10.11.0:mechanism.typeto errors cConfiguration
📅 Schedule: Branch creation - "before 7am on monday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.